home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20031118-20041115
/
000329_fdc@columbia.edu_Wed Jul 14 15:49:53 2004.msg
< prev
next >
Wrap
Internet Message Format
|
2004-11-14
|
2KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Terminal parameter not being set properly from Dialer
Date: 14 Jul 2004 19:48:24 GMT
Organization: Columbia University
Lines: 27
Message-ID: <slrncfb3g8.6l6.fdc@sesame.cc.columbia.edu>
References: <xaOdneIj2cqXF2jd4p2dnA@giganews.com>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1089834504 311 128.59.59.56 (14 Jul 2004 19:48:24 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 14 Jul 2004 19:48:24 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15078
On 2004-07-14, George Matey <gmatey@127.0.0.1> wrote:
: I'm connecting to a device using telnet from the Kermit Dialer (K-95 2.1.3)
: and am getting a local echo. The Local Echo parameter is unchecked in the
: Dialer-Terminal-config GUI. The Generated Script File from the Dialer for
: that device also shows an entry of: "set term echo off", but when it
: connects, there is some echoing. If I enter "set term echo off" from the
: command screen, then all is well for that session.
:
: Since the dialer script is executed last, it also looks like the "set term
: echo off" that I added to my k95custom.ini file is also being
: ignored/overwritten.
:
: I'm unsure where is parameter is being set improperly and where it can
: "fixed".
:
Telnet protocol says that the client echoes locally unless the server offers
(by well defined Telnet protocol negotiations) to echo, which evidently does
no happen in your case. This is one of those confusing cases where certain
things happen before or after certain other things. You tell Kermit not
to echo locally, but then the Telnet startup sequence goes to local echo
automatically because that's part of the Telnet protocol definition, thus
overriding your "set term echo off" command. The trick is to "move" that
command someplace where it will be executed after the Telnet protocol
startup sequence, such as the login script or the key map. Just enter the
command into the text box on the appropriate Dialer entry page.
- Frank